Skip to content

[v20.x] backport V8 changes related to compile cache#56711

Closed
joyeecheung wants to merge 221 commits intonodejs:v20.x-stagingfrom
joyeecheung:backport-cache-fixes
Closed

[v20.x] backport V8 changes related to compile cache#56711
joyeecheung wants to merge 221 commits intonodejs:v20.x-stagingfrom
joyeecheung:backport-cache-fixes

Conversation

@joyeecheung
Copy link
Copy Markdown
Member

This backports the following bug fixes in V8 that are related to compile cache.

https://chromium-review.googlesource.com/c/v8/v8/+/4998581
https://chromium-review.googlesource.com/c/v8/v8/+/4962094
https://chromium-review.googlesource.com/c/v8/v8/+/5401780
https://chromium-review.googlesource.com/c/v8/v8/+/6140933

The motivation of backporting these is that they would help backporting compile cache to v20.x, which would in turn help backporting require(esm) because the two are a bit intertwined in the module compilation/format detection routine, so there would be more conflicts if we backport require(esm) without backporting the compile cache.

One of them fixes in-isolate compilation cache hit for comepileFunction() and another fixes import() when code cache is used, which may be meaningful in themselves for use cases like Jest (e.g. jestjs/jest#15461).

Refs: #52697

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to build files or the CI. needs-ci PRs that need a full CI run. v8 engine Issues and PRs related to the V8 dependency. v20.x Issues that can be reproduced on v20.x or PRs targeting the v20.x-staging branch.

Projects

None yet

Development

Successfully merging this pull request may close these issues.